-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix "mount failed: File exists" issue when unmount fails #4393
Conversation
Welcome @fenglixa! |
Hi @fenglixa. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Can one of the admins verify this patch? |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: fenglixa If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@minikube-bot ok-to-test |
@minikube-bot OK to test |
1 similar comment
@minikube-bot OK to test |
/retest |
@fenglixa: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
/retest this please |
test timed out after 1h15m0s |
It cannot work when I call "/retest" to trigger integration test. Could anyone (member) help on this? |
/retest |
@minikube-bot OK to test |
FYI - minikube has not moved to prow yet, so /retest does not work. We're still stuck on the old-style Jenkins commands. |
Fix for mount failed: mkdir: cannot create directory '/mnt/data': File exists #4239
Why this fix:
Before the fix, the unmount will be always return success, that will cause: a) unmount err message cannot be reported timely. b) force unmount will be never ran.
The fixes including: a) fix above error b) delete corpse processes before unmount.
case-1: a) minikube mount b) minikube ssh; cd c) Ctrl+c d) 'minikube mount' again.
case-2: a) minikube mount b) minikube ssh; run script under mount point dir c) Ctrl+c d) 'minikube mount' again.
/assign @tstromberg
Could you please help review? Thanks.